User-Agent: Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b2pre Thunderbird/3.0.4 Here's the case: I compose a message, then I save it to the DRAFTS folder. Later I open it again and send it. When sending, the message is saved to SENT and TRASH. But TRASH doesn't make sense. Shouldn't be saved to TRASH at all ! Remark: I use Googlemail. Maybe it has something to do with it. Reproducible: Always

Amendment: It's an IMAP GoogleMail Account.

Further Amendment: When TB saves the message a second time to TRASH, of course that message in TB's TRASH is also synced to GMail's TRASH (Web Interface). -- When I test the same case (1. Save to DRAFT; 2. Send) directly via GMail's Web Interface, this problem doesn't occur (which means then the message is only saved to GMail's/TB's SENT - not to GMail's/TB's TRASH a second time).

Closing as DUP of your new bug 562767. Please don't open multiple bugs at B.M.O for same issue. Bug summary change, addition of comments for new findings or problem detail are sufficient.

Before I opened these two bugs, I really thought about, whether Bug 562748 and Bug 562767 might belong together. But then I assumed that they are not dups to each other, but might somehow be related to each other: Bug 562748: The necessary Starting Point is solely TB. Only concerns TB's DRAFTS folder. Has nothing to do with mail attachments. Bug 562767: The necessary Starting Point is solely GMail's Web Interface. Only concerns mails with attachments. Has nothing to do with TB's DRAFTS folder. -> In the end, in both bugs the results might be interpreted more or less as the same. -> But at least the trigger is completely different in both bugs. Therefore I didn't mix up both in a joint bug, because then this big one might have become "unreadable". ==> So I am still not sure, if these two bugs are dups to each other: I always ask myself: would fixing one of them really fix the other one, too ? ==> If they are not dups to each other, can you please re-open this bug here again ? And/Or relate both bugs to each other (make them depend on each other), if this is the case) ? Thanks a lot.

> If they are not dups to each other, can you please re-open this bug here again? Yes, I can change bug's status. > And/Or relate both bugs to each other (make them depend on each other), if this is the case) ? Yes. Depends On: or Blocks: field can be used for xref, although correct use of these fields is for dependency among patches. > Bug 562748: > The necessary Starting Point is solely TB. > Only concerns TB's DRAFTS folder. > Has nothing to do with mail attachments. What does "Starting Point is solely TB" mean? Mail is composed by Tb? Which Gmail folder at Web or IMAP folder for Tb do you Mean by "TB's DRAFT folder"? Can you do step by step check? Can you state detailed "Steps to reproduce problem"?

> What does "Starting Point is solely TB" mean? Mail is composed by Tb? ------------------ Yes, Mail is composed in TB. > Which Gmail folder at Web or IMAP folder for Tb do you Mean by "TB's DRAFT folder"? ------------------ (Analogous to your wording in Bug 562767:) It's the following folder presented in TB: [Gmail]/Drafts ("Drafts" under "[Gmail]", Gmail's folder name=drafts) = Gmail's standard folder for Drafts. > state detailed "Steps to reproduce problem"? ------------------ Due to my limited technical knowledge respectively my lack of the correct technical phrases, I guess more or less I can just repeat the steps I stated in my bug's description (sorry for this), but I'll do my best: 1.) Compose a new message in TB 2.) Instead of sending, save that message to [Gmail]/Drafts folder by Tb via Gmail IMAP 3.) Open that saved message again in TB 4.) Send this message now in TB 5.) Message is saved to [Gmail]/Sent Mail folder by Tb via Gmail IMAP 6.) A duplicate of this message is also saved to [Gmail]/Trash folder by Tb via Gmail IMAP, what should not happen

It sound similar problem to bug 562767(I guess basically same problem of Gmail/Gmail IMAP as bug 562767). However, steps to reproduce/external symptom is different from bug 562767. Re-opening, with setting dependency to bug 562767 for ease of tracking.

Phenomnon was observed by; (0) Tb's draft folder = [Gmail]/Drafts IMAP Delete model : remove immediately (1) Compose a mail by Tb 3.0.x, subject:t01, save, subject:t02, save, ..., subject:t10 save => upon each save, old version appears in [Gmail]/Trash, thus mail of subject:t01 to subject:t09 appear in [Gmail]/Trash. Was big change made on Gmail/Gmail IMAP recently? When do you see this phenomenon first time?

Not [Gmail]/Drafts only issue. Same phenomenon was observed with draft folder choice of root-level "Drafts"(Gmail Label=[Imap]/Drafts) and "A"(Gmail Label=A). It looks phenomenon on mail flagged as \Draft. append "A" with flag \Draft (version-01, uid=U01) append "A" with flag \Draft (version-02, uid=U02) search old version, uid U01 store flag \Deleted => Because draft mail(with \Draft flag), Gmail moves the mail from "All Mail" of Gmail(==[Gmail]/All Mail) to "Trash" of Gmail(==[Gmail]/Trash via Gmail IMAP). Old draft mail shown in [Gmail]/Trash didn't have \Draft flag. \Seen only. In draft case, the old version of draft mail(version-01) was shown in "Trash" folder at Gmail Web Interface too. This is a difference from bug 562767.

Re: questions from comment 8 I am not aware of any recent GMail / IMAP change. I saw this phenomenon for the first time, when I reported this bug here. But of course this does not necessarily mean, that this is really a new problem. Because normally I do not look into my [gmail]/trash folder very often. Just did it by chance. So maybe I only never became aware of this problem before.

People using both TB (with an IMAP connection to Gmail) and Gmails mobile App are affected by the annoying problem described below, related to this bug. When writing long emails in TB the AutoSave function will save several copies of the email in the Draft folder (Gmail Draft folder over IMAP). Every new draft copy moves the old draft copy to the Gmail Trash folder. This is OK when using TB or the Gmail Webb client since they don't show the trashed copies but the Gmail mobile app however includes the trashed copies in the conversation. A conversation in the Gmail mobile App can therefore contain tenfold of almost similar copies of the mail making the whole conversation unreadable. This is a problem that has been around for years and preferably Google should change the App to behave in a similar way as the Webb version. Since nothing has happened from their side for years the question now is if something could be done to TB? The Gmail Webb client permanently deletes replaced drafts (instead of moving them to Trash) so a setting in TB where one could choose to trash or to permanently delete replaced drafts would make the day for a lot of frustrated people out there. An option under settings or the Configuration Editor would be fine.

(In reply to Mikael from comment #13) > People using both TB (with an IMAP connection to Gmail) and Gmails mobile App > are affected by the annoying problem described below, related to this bug. >(snip) > An option under settings or the Configuration Editor would be fine. It's being processed by bug 673400.

Sorry, I misunderstood that "no \Seen of saved draft by Tb" is cause. (In reply to Mikael from comment #13) > When writing long emails in TB the AutoSave function will save several > copies of the email in the Draft folder (Gmail Draft folder over IMAP). > Every new draft copy moves the old draft copy to the Gmail Trash folder. >(snip) > but the Gmail mobile app however includes the trashed copies in the conversation. > A conversation in the Gmail mobile App can therefore contain tenfold of > almost similar copies of the mail making the whole conversation unreadable. Even though you know problem of Google mobile app well and you know cause and you are suffering from the problem very much, why you still save draft(an large) by Tb to [Gmail]/Drafts? I can't imagine why next is mandatory for you even though you are suffering from the problem. Create big draft mail by Tb, save in [Gmail]/Draft, View the big draft and/or Edit the big draft mail on mobile device and save, Send the big draft by mobile device or by Tb on PC. Why Drafts of "Local Folder" of Tb is not usable in you case? Why can it be "save draft to [Gmail]/Drafts by Tb" only problem? Same thing happens too when draft is saved to [Gmail]/Drafts by mobile device, doesn't it? Even when deleted draft mails are held in [Gmail]/Trash by Gmail, any mail in [Gmail]/Trash can be purged immediately by "Empty Trash" at [Gmail]/Trash of Tb. Why you don't do such action even though you are suffering from the Google mobile app problem very much? If mail is sent using Google's SMTP, sent mail copy is saved in [Gmail]/Sent and [Gmail]/All Mail by Gmail's SMTP/Gmail. Does the Google mobile app access mails via IMAP? Is this two mails also shown in conversation as done on mails in [Gmail]/Trash? Or is the Google mobile app Web app? Does he see "All Mail", "Trash" (and "Spam") folder of Gmail(not Gmail IMAP folder)? Have you requested Google to resolve the problem of Google mobile app? (as Google mobile app problem, it should be reported to Google first, instead of bugzilla.mozilla.org)

(In reply to WADA from comment #15) > Even though you know problem of Google mobile app well and you know cause > and you are suffering from the problem very much, why you still save > draft(an large) by Tb to [Gmail]/Drafts? I can't imagine why next is > mandatory for you even though you are suffering from the problem. > Create big draft mail by Tb, save in [Gmail]/Draft, > View the big draft and/or Edit the big draft mail on mobile device and > save, > Send the big draft by mobile device or by Tb on PC. > Why Drafts of "Local Folder" of Tb is not usable in you case? I would like to point out that it's the normal Autosaving function during normal compose that gives the problem. I am not manually viewing or editing the drafts from TB, the mobile device or the Gmail Webb Page. To use a Local Folder for TB Drafts is a good idea and it indeed solves the problem with multiple copies in the conversation. The drawback is that you then limit the complete sync between platforms. An unfinished mail can only be picked up and completed by TB on the original computer. This might not be a big issue for most users however. > Why can it be "save draft to [Gmail]/Drafts by Tb" only problem? > Same thing happens too when draft is saved to [Gmail]/Drafts by mobile > device, doesn't it? When composing mails from a mobile device with Googles Gmail App the most recent draft is saved under drafts but the older drafts are permanently deleted and NOT copied to the Trash. The same goes for the Gmail Webb "program". Also TB seems to behave this way when it's not under an IMAP connection. If the Draft folder is set to be a local folder only the most recent draft is kept and nothing is moved to any Trash bin. This makes me think that a change of the IMAP behaviour could be valid > If mail is sent using Google's SMTP, sent mail copy is saved in > [Gmail]/Sent and [Gmail]/All Mail by Gmail's SMTP/Gmail. > Does the Google mobile app access mails via IMAP? Is this two mails also > shown in conversation as done on mails in [Gmail]/Trash? > Or is the Google mobile app Web app? Does he see "All Mail", "Trash" (and > "Spam") folder of Gmail(not Gmail IMAP folder)? Emails in [Gmail]/Sent are visible in the conversation. I'm however not sure how the Gmail Android App works under "the hood". Google recomends on their Webpage for TB settings to store Message Drafts directly under [Gmail]/Drafts. > Have you requested Google to resolve the problem of Google mobile app? > (as Google mobile app problem, it should be reported to Google first, > instead of bugzilla.mozilla.org) As I wrote in my first note I agree with you that a change of the Google Gmail mobile App would be the logic thing to do. It's however very hard to get in direct contact with Google (they don't have such an eminent tool as Bugzilla). The issue with trashed drafts visible in the conversation on mobile Gmail app is discussed in numerous threads on Googles help pages with a lot of people having the same problem but there seem to be no responce from Google yet. Since TB is inconsequent in how to handle removed drafts (move them to trash or delete them) I think that a "bug fix" could be motivated. Please note that I'm not a programmer or computer engineer in any way and that my previous post was my first here on Bugzilla. I'm a total newbee when it comes to IMAP and such tings so some of my writing here might seem dumb or incorrect. I however think it would be a good idea to try to do somthing about this issue since I know people that abandons TB just because this "messing upp in the Conversation" thing. Since more and more people read their emails on mobile devices this issue might grow. Over and Out.

Hi, according to this forum post: https://productforums.google.com/forum/?fromgroups#!topic/gmail/j-zuvSHohF4 its a client (thunderbird) issue. Gmail save the draft overwriting the previous one and delete it after successfully sending the message. So this is a thunderbird bug. Can you fix it? thanks! (that forum is the only official support channel for android applications -- no bug public tracker)

Would not changing the drafts folder in account settings to local folders instead of the gmail drafts folder make a simple and concise workaround? I doubt many people are composing the same mail across multiple devices.

Actually I DO compose emails across multiple devices. I often start writing an email, on my phone then come home, and use the laptop or viceversa. And I'm not only talking about manual save but automatic saves.

(In reply to Daniele Segato from comment #18) > its a client (thunderbird) issue. Yes. It's phenomenon observed in Tb, because Tb shows mails in [Gmail]/Trash. > Gmail save the draft overwriting the previous one and delete it after > successfully sending the message. It's for draft mail generated by Gmail(Gmail's Web mail) and sent mail by Gmail(Gmail's Web mail), isn't it? > So this is a thunderbird bug. How it can be Tb's bug? Tb correctly stores \Deleted flag to draft mail saved in [Gmail]/Drafts after new draft save or mail send, according to IMAP design/spec/implementation. Why can this bug be Tb's bug==flaw in Tb's code? Please note that I know "move draft mail to be deleted to [Gmail]/Trash, then store +Flags \Deleted at [Gmail]/Trash" is a workaround of funny behavior of this bug by Gmail/Gmail IMAP on deleted draft mail in [Gmail]/Drafts due to special spec of Gmail/Gmail IMAP.

(In reply to WADA from comment #21) > (In reply to Daniele Segato from comment #18) > > its a client (thunderbird) issue. > > Yes. It's phenomenon observed in Tb, because Tb shows mails in [Gmail]/Trash. ok, I do not know how it works internally. I was just quoting what's in here: https://productforums.google.com/forum/?fromgroups#!topic/gmail/j-zuvSHohF4 so you say this is Gmail / Gmail for Android being dump and showing the trash emails in the conversation, am I right? > > Gmail save the draft overwriting the previous one and delete it after > > successfully sending the message. > > It's for draft mail generated by Gmail(Gmail's Web mail) and sent mail by > Gmail(Gmail's Web mail), isn't it? > Actually any gmail client from google. > > So this is a thunderbird bug. > > How it can be Tb's bug? > Tb correctly stores \Deleted flag to draft mail saved in [Gmail]/Drafts > after new draft save or mail send, according to IMAP > design/spec/implementation. > Why can this bug be Tb's bug==flaw in Tb's code? > > Please note that I know "move draft mail to be deleted to [Gmail]/Trash, > then store +Flags \Deleted at [Gmail]/Trash" is a workaround of funny > behavior of this bug by Gmail/Gmail IMAP on deleted draft mail in > [Gmail]/Drafts due to special spec of Gmail/Gmail IMAP. So you are claiming this is a bug in the IMAP implementation in Gmail, am I right? Mind filing a detailed bug to them? You seem more prepared them in on the matter. Thanks

Would it really interfere with the IMAP specification if the old "trashed draft" got permanently deleted when a later draft gets the deleted flag??? This is all that is needed to fix this TB/G-mail problem. Other e-mail programs seems to handle this without any problem and TB does it when not in IMAP. I agree with Daniele, I also compose emails across multiple platforms and I know many other that does. I think it's unneccessary to argue about if this is Googles or TB:s fault. The issue can be solved within TB and in that way making TB a better product. As I have stated before a small checkbox can be added in the settings somewhere enabling compability with Android Gmail app. How many Android/Gmail users are there out there? All of them would be affected of this if they try to use TB. I'm therefore a bit confused that no TB developer has taken on this issue! Regards /Mikael

(In reply to Mikael from comment #23) > Would it really interfere with the IMAP specification if the old "trashed > draft" got permanently deleted when a later draft gets the deleted flag??? Unfortunately, that is not how GMail IMAP works. Even if you use the IMAP protocol to "permanently delete" a message in Thunderbird, the GMail server automatically moves the message to the [GMail]/Trash folder. > I'm therefore a bit confused that no TB developer has taken on this issue! The bug to developer ratio is a bit in favor of bugs at the moment. We will take all the help we can get! In the mean time, I have developed an extension that can help with this problem. It allows auto-saved drafts to be saved to your Local Drafts folder (not on the server). This keeps the Trash folder on GMail from being filled up with the auto-saved copies, but you can still save regular drafts to the Gmail Drafts folder for cross device composing of messages. https://addons.mozilla.org/en-US/thunderbird/addon/auto-save-drafts-folders/ I would like to see this built into Thunderbird rather than as an extension, but as a volunteer, it takes me quite a while to getting around to doing things like this. Here's to hoping that I make time one day.

Oh, so it is not possible to actually remove a message from the GMail server over IMAP?? If that's the case, that any IMAP deleted message just ends up in the Trash folder no matter what I agree with you that this really is Google/GMails fault and it makes it increadibly hard to understand why they include also the trashed copies in the Android Gmail App conversations. Anyone who knows how the Android Gmail App communicates with the Gmail server? Because obviously the permanent deleting of drafts works here. I will defenitely try your add-on Dlech. Thanks for the work and efforts all of you put into the program! I understand that it can be a bit frustrating when people like my self demands new features that we don't really know anything about but at the end of the day we all share the same interest of developing TB to even higher levels. Cheers!

(In reply to Mikael from comment #16) > Googles help pages with a lot of people having the same problem > but there seem to be no response from Google yet. Have you looked Google Apps forum etc., before adding many complaints on Tb and Tb developer at bugzilla.mozilla.org, even though cause is bug(actual flaw in code) of Android Google Apps instead of Tb's problem nor Gmail bug nor Gmail IMAP bug? Does the Androd Google Apps bug occurs on old draft mails deleted by Tb only? It occurs on any mail which is copied/moved to [Gmail]/Trash via IMAP by any IMAP client, doesn't it? It's simply "if auto-save of Tb is used, many deleted draft mails in [Gmail]/Trash easily happens by co-operation of Tb and Gmail/Gmail IMAP, so editing draft by Android is pretty tough work", isn't it? Following is web pages for "Empty Gmail Trash on Android" which are pretty easily found by Google Search for "android gmail application [Gmail]/Trash". > http://www.addictivetips.com/android/delete-all-emails-in-your-gmail-trash-folder-from-android/ > Relatively new, because dated "January 10, 2013" (some others) > http://www.findmysoft.com/news/Empty-Gmail-Trash-EGT-App-Works-Like-A-Charm/ > http://forums.androidcentral.com/google-nexus-7-tablet/215885-how-empty-gmail-trash.html > http://androidforums.com/samsung-galaxy-nexus/492853-emptying-trash-in-gmail.html >(snip) Even if you use auto-save-drafts-folders addon with "auto-save == local folder, save as draft == [Gmail]/Drafts", if you execute manual Save As multiple times in Tb or in other IMAP clients, and if you never execute "Empty Trash" of Tb on Gmail IMAP account, same problem surely occurs, although number of "deleted draft mails shown by Android in coversation" is reduced pretty much by the add-on. Try this quick solution of "Empty Gmail Trash" too.

Changing bug summary, to avoid further useless commant like "this is Tb's bug!".

I have been doing some investigations and to me it is now obvious that it is possible to remove messages from the Gmail Trash folder from an IMAP client. This problem with Android Gmail App showing TB:s trashed autosave drafts can then be solved from within TB. All that is needed is that TB, whenever autosaving a new version of the draft, deletes the old version twice. First from the Draft folder (moving it to trash) and then again from Trash which means it is deleted permanently. For more details see: https://support.google.com/mail/answer/77657?hl=en https://support.google.com/mail/answer/78755 I'm not saying that this is TB:s bug but it is obviously possible to handle this in a way that deleted drafts don't end up in the trash so why not do it, or at least give the user an option not to do it? There is no "law" saying that deleted drafts must remain in trash. Best regards

I just want the trash folder not shown as unread ( bold fonts, unread numbers). Is it possible?

Just happened to me on TB/Kubuntu: compose a mail, Send it, find it in Sent (good) and twice in Bin (not so good)

(In reply to Mikael from comment #28) > All that is needed is that TB, whenever autosaving a new version of the > draft, deletes the old version twice. First from the Draft folder (moving it > to trash) and then again from Trash which means it is deleted permanently. > > For more details see: > https://support.google.com/mail/answer/77657?hl=en > https://support.google.com/mail/answer/78755 Also https://productforums.google.com/forum/#!topic/gmail/kigJGAx_kmo ... among others Thanks to dlech for https://addons.mozilla.org/en-US/thunderbird/addon/auto-save-drafts-folders/

Been seeing this in SeaMonkey Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:41.0) Gecko/20100101 Firefox/41.0 SeaMonkey/2.38 Build identifier: 20150903213426

Hello, the situation here seems to have improved somewhat for me, although drafts that are composed in Thunderbird do pile up multiple drafts in gmail web and mobile app before sending, once sent from Thunderbird they all disappear. It seems like they disappear once I refresh my Drafts/Sent folders in Thunderbird, although that could be coincidence. However drafts that are started in Thunderbird, resulting in multiple copies in gmail, and then are sent from web or mobile app, do still leave behind the old draft copies, visible in the web or mobile drafts folder. Changing the 'immediately delete' gmail setting does not make a difference. So I guess the potential fix is still the same as what was discussed in comment #28. (I am aware that this is not really Thunderbird's bug) Has there been any further investigation on this? It would be nice to autosave to gmail. Perhaps even a plugin could do the double delete on draft overwrite?